home *** CD-ROM | disk | FTP | other *** search
- Path: pinnacle.co.nz!not-for-mail
- From: jonc@pinnacle.co.nz (Jonathan Chen)
- Newsgroups: comp.os.linux.misc,comp.lang.c,comp.unix.admin,comp.security.unix
- Subject: Re: binaries (generated from "C" code)
- Date: 28 Mar 1996 17:02:07 +1200
- Organization: Pinnacle Software Ltd, Auckland, New Zealand
- Message-ID: <4jd6gf$6ff@tui.pinnacle.co.nz>
- References: <4j7pge$9ga@xanadu.io.com> <hendersoDovvs3.20G@netcom.com> <4ja11e$e1m@mpro1.mpro.net>
- NNTP-Posting-Host: tui.pinnacle.co.nz
- X-Newsreader: NN version 6.5.0 #3 (NOV)
-
- In <4ja11e$e1m@mpro1.mpro.net> larry@pronet.mpro.net (Larry Motylinski) writes:
-
- [snip]
- >What I used to do is read the CMOS and other eproms (looking for a
- >serial number or something that made it unique) and then encrypt that
- >code in a program. The program (when run) would verify this
- >information. It kinda sucks because you will be the one to get a call
- >if they change their hardware. I used to use the lower memory block
- >in dos to see what hardware they had and build that into the program
- >also. Another trick I used to use was using tracks on a floppy that
- >didn't technically exist (track 81) and that only worked with very
- >low-level programming (I used assembler to access the track).
- >
- >Hope this helps
-
- And how portable would this be to UNIX systems in general?
- --
- Jonathan Chen <jonc@pinnacle.co.nz>
- --
- ~/.signature: Permission denied
-